Skip to content

Pass through TLB date metadata and invalidate loan balance cache#670

Closed
jforseth-figure wants to merge 2 commits into
mainfrom
jforseth/tlb-changes
Closed

Pass through TLB date metadata and invalidate loan balance cache#670
jforseth-figure wants to merge 2 commits into
mainfrom
jforseth/tlb-changes

Conversation

@jforseth-figure

@jforseth-figure jforseth-figure commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Related PRs

Deploy order: go-pulse-service → explorer-service → pulse-service / frontend-provenance-pulse


Description

closes: #XXXX


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Wrote unit and integration
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer
  • Review Codecov Report in the comment section below once CI passes

Surface asOfDate and dataStartDate on loan balance metrics and clear
stale pulse_cache rows after go-pulse-service aggregation changes.
@@ -0,0 +1,7 @@
-- Invalidate cached Total Loan Balance metrics after aggregation logic change.
-- Cached entries will be rebuilt on next request with the updated go-pulse-service query.
DELETE FROM pulse_cache

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This deletes the entire history of these metrics. Are we sure that's what we want to do? If so, are we able to backfill and rebuild the history?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like it's definitely :badvibes: I should've caught.

But how should we handle the old data? Just leave it be and show a drop in TBL? Backfill using a different approach?

We can manually clear part of the cache as needed, but clearing everything is probably a bad idea.
@jforseth-figure jforseth-figure marked this pull request as ready for review June 29, 2026 20:40
@jforseth-figure jforseth-figure requested a review from a team as a code owner June 29, 2026 20:40
@jforseth-figure

Copy link
Copy Markdown
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants